New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop runs-per-test for unit tests #98272
Conversation
/kind cleanup |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt, spiffxp The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
go has a runs per test equivalent (-count) is the test time really too long? |
setting that makes you lose the ability to use the test cache :-/ |
/retest hit a (not reproducible locally using
|
/retest Review the full test history for this PR. Silence the bot with an |
Cherry-pick of kubernetes#98272 Related to b/177937814 Change-Id: I8e5e69e22158a3fdf6bb816c83219e4daad1087d
This was added on the assumption that we could use bazel test result caching.
Since we can't this actually doubles the runtime (or resources) of every unit test run.
Without this, flakes can still be seen in the triage board or periodic runs.
Whittling down bazelisms in our test configs ahead of #97921
/cc @BenTheElder